how do i make bsd CI run in this PR?

You cannot anymore. Only my PRs are checked for BSDs as Sourcehut complained about the tremendous resource consumptions that the Nim project causes. No, I'm not kidding.

You cannot anymore. Only my PRs are checked for BSDs as Sourcehut complained about the tremendous resource consumptions that the Nim project causes. No, I'm not kidding.

I'm aware of that issue, but the fact that only 1 person can run BSD tests is not good; there's a huge difference between running bsd CI in all PR's on each commit, vs allowing an opt-in [ci bsd] or equivalent that would probably involve < 1% of all PRs/commits.

I'm fairly certain @ddevault would be ok with that? /cc @ddevault

Hm, not really. [ci bsd] does not jive with how we designed builds.sr.ht. We could accomodate you on git.sr.ht, but probably not through the dispatch portal to github.

So how do we proceed on our end? All that's needed is an opt-in way to allow running CI against our builds.sr.ht pipelines; it's expected to not be frequently used so shouldn't result in large resource use.

If [ci bsd] doesn't work, how about a .builds/openbsd.yml.disabled that PR authors would temporarily enable while working on a fix involving BSD, and that would run whenver the .disabled extension is removed?

It's not about the resource use, it's about the design and maintenance cost of an on-demand feature.

@timotheecour

Only my PRs are checked for BSDs

Not really, the members of Nim-lang can create a new branch, then the PR can be checked on BSDs too.

So you need to clone the nim-lang/Nim directly and make a new branch then push it.